Replace the deprecated PrivateSentrySDKOnly SPI and SentrySwizzle.h macro
with the new SentrySDK.internal Swift API exposed by sentry-cocoa 9.19.0,
via a thin in-pod ObjC<->Swift bridge (RNSentryInternal.swift). Imports
Sentry with @_spi(Private) for SPI-gated sub-APIs (performance, replay,
envelope). Drops the performSelector workaround around getReplayIntegration
since SentrySDK.internal.replay.capture() returns Bool directly.

Closes #6370

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

`withUnsafePointer(to:)` only guarantees the pointer stays valid inside
the closure body. Capturing it in `keyPtr` and using it outside the
closure was undefined behaviour by contract (even though `static var`
storage happens to be stable in practice). Wrap the entire
`instanceMethod` call inside `withUnsafePointer` so the pointer is
always used within its documented lifetime; the `static var` backing
storage keeps the address itself stable across calls, so sentry-cocoa's
`oncePerClass` dedup keeps working.

Flagged by Cursor Bugbot.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Handle both static-lib and framework-style Pod integrations by falling
back from `<RNSentry/RNSentry-Swift.h>` (frameworks path) to the local
`"RNSentry-Swift.h"` (static-lib path) via `__has_include`. Applied to
every `.m`/`.mm` in packages/core/ios that consumes the Swift bridge.

Suggested by @antonis.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Two fixes flagged by Warden:

1. `RNSentryInternal.envelope(fromData:)` accepted a non-optional Swift
   `Data`. If the ObjC caller passed a nil `NSData*` (e.g. from a failed
   base64 decode of the envelope payload), the ObjC→Swift bridge would
   force-unwrap it and crash before the method body ran. Change the
   parameter to `Data?` with an internal `guard let` — matches the
   nil-tolerant behaviour of the deprecated
   `PrivateSentrySDKOnly.envelopeWithData:`.

2. Swift Cocoa tests accessed `SentrySDK.internal.*` with plain
   `import Sentry`. The `.internal` accessor is public today, but the
   sub-APIs the tests touch (`options`, `appStart`, `performance`) sit
   next to `@_spi(Private)`-gated siblings on the same struct. Add
   `@_spi(Private) import Sentry` to `RNSentryStartTests.swift`,
   `RNSentryStartFromFileTests.swift`, and `RNSentryReplayOptionsTests.swift`
   so they keep compiling if the surface is ever tightened.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

When `captureViewHierarchy` returned nil the ObjC code still constructed
an empty `NSMutableArray` and resolved with it. In JS, `[]` is truthy —
the caller would treat the failure as a successful (empty) attachment.
Bail out with `resolve(nil)` up front so the JS side sees the actual
failure signal.

Pre-existing since 2023; flagged by Seer while reviewing this PR.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Cover the bridge's own contract — nil-guard on `envelope(fromData:)`,
metadata accessors, options factory, hybrid-SDK-mode flags, and the
`swizzleRNSScreenViewDidAppear` early-return when RNSScreen is
unavailable. sentry-cocoa owns the underlying `SentrySDK.internal.*`
behaviour; we just assert the wrapper forwards correctly and honours
the documented nil / platform guards.

Registers the new file in the RNSentryCocoaTester project explicitly
(the target does not use file-system-synchronized groups yet).

Flagged by Warden.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Adding Swift to the RNSentry pod means CocoaPods refuses to integrate it
against non-modular ObjC dependencies. On older React Native versions
(e.g. 0.71 with Hermes) the React-hermes pod does not define modules, so
`pod install` fails with:

  The Swift pod `RNSentry` depends upon `React-hermes`, which does not
  define modules.

Inject `use_modular_headers!` into the Podfile via the existing e2e patch
script, and document the same knob for downstream users in the CHANGELOG.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Cherry-picked from #6410. Dependabot bumped `codeql-action/analyze` and
`codeql-action/autobuild` to v4.36.3 but left `init` on v4.36.2, so
`init` writes a config stamped 4.36.2 that `analyze` (4.36.3) rejects:

  Loaded a configuration file for version '4.36.2', but running version '4.36.3'

Pull this fix into the PR branch so CI stops failing while #6410 is
still open on main.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Previous version unconditionally set `modularPatched = true` inside the
`use_modular_headers!` branch, so a Podfile without a
`prepare_react_native_project!` anchor would be reported as successfully
patched even though `content.replace` returned it unchanged.

Compare replace output against the input and log a warning instead when
the anchor is missing.

Flagged by Cursor Bugbot.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

The migration to `SentrySDK.internal.screen.setCurrent` drops the
current-screen breadcrumb enrichment on visionOS because sentry-cocoa's
new `SentryInternalScreenApi` is gated to iOS/tvOS only. Already
documented in a code comment; call it out for downstream users too.

Flagged by Seer.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

`RNSentryInternal` is a Swift type compiled into the `RNSentry` pod
module, not the `Sentry` module. Without `@_spi(Private) import RNSentry`
the test target cannot resolve `RNSentryInternal.*` and fails to build.

Flagged by Warden.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>